chore(deps): update dependency gettext to ~> 0.26 #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~> 0.18->~> 0.26Release Notes
elixir-gettext/gettext (gettext)
v0.26.2Compare Source
message and conflicting plural messages.
Gettext backend.
v0.26.1Compare Source
v0.26.0Compare Source
This release changes the way you use Gettext. We're not crazy: it does so because doing so makes it a lot faster to compile projects that use Gettext.
The changes you have to make to your code are minimal, and the old behavior is deprecated so that you will be guided on how to update.
The reason for this change is that it removes compile-time dependencies from modules that used to
importa Gettext backend. In applications such as Phoenix applications, where every view and controllerimports the Gettext backend, this change means a lot less compilation when you make translation changes!Here's the new API. Now, instead of defining a Gettext backend (
use Gettext) and thenimporting that to use its macros, you need to:use Gettext.Backenduse Gettext, backend: MyApp.Gettext.Before and After
Before this release, code using Gettext used to look something like this:
This creates a compile-time dependency for every module that
imports the Gettext backend.With this release, the above turns into:
We are also updating Phoenix generators to use the new API.
If you update Gettext and still use
use Gettext, otp_app: :my_appto define a backend, Gettext will emit a warning now.Migration with Igniter
If your project is using
igniter, you can runmix igniter.update_gettextto automatically migrate to the new API.
Detailed Changelog
This is a detailed list of the new things introduced in this release:
Gettext.Macros, which contains all the macros you know and love (*gettext). It also contains*gettext_with_backendvariants to explicitly pass a backend at compile time and keep extraction working.lgettext/5andlngettext/7callbacks inGettext.Backend. These get generated in every Gettext backend.Gettext.domain/0type.v0.25.0Compare Source
mix gettext.extract's POT files even if they are unchanged.v0.24.0Compare Source
Handle singular and plural messages with the same
msgidas the samemessage.
This change produces a
Expo.PO.DuplicateMessagesErrorif you already havemessages with the same singular
msgid. This can be solved by calling theexpo.msguniqmix task on your.pofile:v0.23.1Compare Source
v0.23.0Compare Source
:custom_flags_to_keepGettext option.v0.22.3Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.